Inquiry-Based Scenario Analysis of System Requirements Colin Potts
نویسندگان
چکیده
منابع مشابه
An evaluation of inquiry-based requirements analysis for an Internet service
The Inquiry Cycle is a generic process model for conducting requirements elaboration. It consists of three activities: requirements expression, discussion and commitment. This paper describes an evaluation of the Inquiry Cycle model and a support tool, Tuiqiao, in the requirements analysis phase of a real project, a proposed commercial consumer information service based on Internet. The extent ...
متن کاملGrounding Scenarios in Frame-Based Action Semantics
Scenarios that describe concrete situations of software operation play an important role in software development, and in particular in requirements engineering. Scenario details should vary in content and detail when described from different viewpoints (e.g. types of user or external interface), but this presents a difficulty, because informal scenarios cannot easily be translated from one view...
متن کاملScenario-based Analysis of Non-Functional Requirements
Scenarios have been advocated as an effective means of acquiring and validating requirements as they capture examples and real world experiences that users can understand [Potts et al. 1994]. Although scenarios have appeared in many diverse forms [Carroll 1995], most authors have used them for behavioural analysis, e.g. scenario scripts [Potts et al. 1994] and use case scenarios [Jacobson et al...
متن کاملAn Active Hypertext Model for System Requirements 1 . Introduction 2 . Conversational Model
We are developing tools to support a conversational metaphor for requirements definition and analysis. Our conversational model consists of three components: (1) a hypertextual representation of requirements and their interrelations, (2) an issue-based speech act model, and (3) a typology of changes. These components act together in a model we call the Inquiry Cycle. We discuss requirements ana...
متن کاملCommunicating Requirements Using End-User GUI Constructions with Argumentation
Unsuccessful communication is often at the root of inadequate requirements specification [14]. This can lead to requirements that do not capture complete stakeholder expectations. Stakeholders can include managers, software engineers, end-users, clients, etc. End-users provide a rich source of information about a system as they will directly interact with the final system. They also tend to hav...
متن کاملذخیره در منابع من
با ذخیره ی این منبع در منابع من، دسترسی به آن را برای استفاده های بعدی آسان تر کنید
عنوان ژورنال:
دوره شماره
صفحات -
تاریخ انتشار 1994